Logging data about multicast streams
To log data about that receive content as a stream, you can use the Multicast and Advertisement Logging Agent, which installs the Windows Media Internet Server Application Programming Interface (ISAPI) extension (wmsiislog.dll).
The Multicast and Advertisement Logging Agent must be installed by an administrator to allow it to write its properties to the registry and is available as an optional component of Windows Media Services setup. After installation it reads its configuration setting from the registry of the Web server it is installed on. For more information on the properties of the ISAPI application, see the ISAPI properties reference. The ISAPI extension is installed in the %systemdrive%\WMPub\Wmiislog folder.
Log files for multicast are saved to the %systemroot%\WMPub\WMIISlog folder. This folder is created automatically when you register wmsiislog.dll. Each log file name uses the WMS_ISAPI_yyyymmdd.log format, where yyyymmdd is the year, month, and day when the log file is created. If more than one log file is generated in a day, an incremented number is added to the file name, using the format WMS_yyyymmdd_iiii.log, where iiii is a number that starts at 0001 and increases by one for every log file generated after the first one. Make sure you have configured Internet Information Services (IIS) to support Internet Server Application Programming Interface (ISAPI) applications so that Wmsiislog.dll can receive logs. You can also write a Common Gateway Interface (CGI) script to generate a log file.
The information that is generated in a log file for a multicast client is the same as information generated by the WMS Client Logging plug-in, except that it does not have server statistics. For information about the fields in a log file, see Log file header reference and Log file entries reference.
Notes
- The log file contains data for all multicast clients receiving a stream from the server, regardless of the . You can also use the ISAPI extension to distribute log files to customers so they can have a record of activity for multicast clients.
- Windows Media Services does not include a logging plug-in for encoder push scenarios. You can log encoder push broadcast data by creating an event notification plug-in or an event notification script for use with the WMS Active Script Event Handler plug-in on your Windows Media server. For more information about creating a custom plug-in, see the Windows Media Services Software Development Kit (SDK), which can be downloaded from the Windows Media home page at the Microsoft Web site.
- The server does not use your user account to access folders and other resources; it uses the Network Service account by default. If you want to save logging information to a file that is in a folder other than %systemroot%\System32\LogFiles\WMS_ISAPI, ensure that the folder is shared and that the Network Service account has read, write, and modify permissions for the folder. If the Network Service account does not have the appropriate permissions for the folder, the server will not be able to save log information to it. For more information about rights and permissions, see Understanding rights.
- Multicast streaming and the WMS Multicast Data Writer plug-in are available only if Windows Media Services 9 Series is running on the following editions of the operating system: Windows Server 2003, Enterprise Edition and Windows Server 2003, Datacenter Edition. If you are running Windows Server 2003, Standard Edition, these features are not supported.
Related topics
© 2000-2003 Microsoft Corporation. All rights reserved.
